Oracle Utilities Customer Care and Billing Configuration AP Request Integration Point Configure the Accounting Entry Template Characteristic Type For each Adjustment Type that has an associated AP Request you will need to identify, in Oracle Utilities Customer Care and Billing, the accounting entry template to be used in Oracle PeopleSoft Enterprise Management GL. This template is used by the Oracle PeopleSoft Enterprise Management applications to determine the offset account associated with the distribution code and GL account information sent from Oracle Utilities Customer Care and Billing with the AP Request information. Complete the following configuration in Oracle Utilities Customer Care and Billing to reference the Accounting Entry Template corresponding to the distribution code as follows. 1. Create a Characteristic TypeAdmin Menu > C > Characteristic TypeThe value for this characteristic type stores the value of the Oracle PeopleSoft Enterprise Management Accounting Entry Template. In this example it is CCBTMPLT. You will use the name of the template you have established for this purpose in Oracle PeopleSoft Enterprise Management. 2. Set up the details on the Characteristic Type as follows: Field Label Value Comments Characteristic Type TEMPLATE The code associated with your characteristic type. This will be used in future steps. Description Oracle PeopleSoft Enterprise Management Template A description of the use for this characteristic type. Type of Char Value Predefined Value No freeform text is allowed, only a set of predefined values. Allow Search by Char Val Allowed Allow Searches Characteristic Value CCBTMPLT The name of the Oracle PeopleSoft Enterprise Management Template to be used. Description CCB Account Template 3. . Select the Characteristic Entities tab to allow the Characteristic Type to be associated with the Distribution Code: Field Label Value Comment Characteristic Entity Distribution Code This characteristic type can be inserted on a distribution code. 4. Attach the Characteristic Type, created above, to any distribution codes that will be used for AP Request Adjustments. An example is provided in demo data as the A/P - OVPY Distribution Code that is attached to the REFUNDAP Adjustment Code. Admin Menu > D > Distribution Code Field Label Value Comment Distribution Code Example: A/P-OVPY The distribution code to be used for financial transactions of a certain type. Description Example: AP overpayment refund A description of how the distribution code is used. GL Account Algorithm GLCNST-DFLT The standard product, or customer modified, algorithm you used for determining the GL Account String from the distribution code. GL Account Details 1 of 1 Create at least one set of account details as needed by your chosen algorithm above. Only one will be used based on status and effective date. Effective Date 01-01-1900 The date you wish the following GL Account string to become active and used by the system, and therefore, the integration software. Status Active Only Active status accounts will be used by the Product and therefore, the integration. GL Account 400000.10000.NEWYORK.ALLPRD......211004 Input the GL Account String as explained above. Characteristic Type Oracle PeopleSoft Enterprise Management Template The characteristic type you created above. Characteristic Value Example: CCBTMPLT The value you gave to the characteristic type created above. Note: Only fields relevant to the integration are included in this table. Configure the AP Business Unit Characteristic Type For each CIS Division used, in Oracle Utilities Customer Care and Billing, the AP Business Unit to be used in Oracle PeopleSoft Enterprise Management GL must be configured. Complete the following configuration in Oracle Utilities Customer Care and Billing to reference the AP Business Unit corresponding to the CIS Division as follows. 1. Create a Characteristic TypeAdmin Menu > C > Characteristic TypeThe value for this characteristic type stores the value of the Oracle PeopleSoft Enterprise Management AP Business Unit. In this example it is CCBTMPLT. You will use the name of the template you have established for this purpose in Oracle PeopleSoft Enterprise Management. 2. Set up the details on the Characteristic Type as follows: Field Label Value Comments Characteristic Type PSBU The code associated with your characteristic type. This will be used in future steps. Description Oracle PeopleSoft Enterprise Management Business Unit A description of the use for this characteristic type. Type of Char Value Predefined Value No freeform text is allowed, only a predefined set of values. Allow Search by Char Val Allowed Allow Searches Characteristic Value US001 The name of the Oracle PeopleSoft Enterprise Management AP Business Unit to be used. Description US001 Business Unit 3. . Select the Characteristic Entities tab to allow the Characteristic Type to be associated with the Distribution Code: Field Label Value Comments Characteristic Entity CIS Division This characteristic type can be inserted on a CIS Division. 4. Attach the Characteristic Type, created above, to any CIS Divisions that will be used for AP Request Adjustments. In sample data an example is provided as the CA CIS Division. Admin Menu > C > CIS Division Field Label Value Comments CIS Division Example: CA The CIS Division to be used. Description Example: California A description of how the CIS Division is used. Characteristic Tab Effective Date Example: 01-01-1900 The date you wish the characteristic type and value to become active and used by the system, and therefore, the integration software. Characteristic Type Oracle PeopleSoft Enterprise Management Business Unit The characteristic type you created above. Characteristic Value Example: US001 The value you gave to the characteristic type created above. Note: Only fields relevant to the integration are included in this table. AP Data Integration Point No Oracle Utilities Customer Care and Billing configuration is required to enable this integration point. AP payment data is extracted from Oracle PeopleSoft Enterprise Management when an AP Request invoice is paid. This data is then translated by the BPEL service and inserted into the Oracle Utilities Customer Care and Billing AP Request that initiated the invoice in the first place. Oracle BPEL Process Manager invokes the Oracle Utilities Customer Care and Billing service, named C1AdjustmentMaintenance, when a payment is canceled and the liability is closed in Oracle PeopleSoft Enterprise Management. The service will use the cancel reason contained in its configuration when canceling the adjustment associated with an AP Request. The sample data cancel reason comes pre-configured as "APVC' (Accounts Payable Void Check) in Oracle Utilities Customer Care and Billing version 2.2 and later. You should verify that the cancel service C1AdjustmentMaintenance is configured and that the Cancel Reason to which it refers is also configured correctly. Admin Menu > X > XAI Inbound Service Field Label Value Comment XAI in Service Name AdjustmentMaintenance This service is used to change data associated with adjustment transactions. Description AdjustmentMaintenance for AP Cancel Long Description AdjustmentMaintenance for AP Cancel Active Checked Active check box checked Request Schema C1AdjustmentMaintenance.xsd Used by BPEL to receive the response from this service. Transaction Type Update Service used to update an existing adjustment transaction You may wish to test this service using XAI Dynamic Submission as follows: Admin Menu > X > XAI Dynamic Submission Field Label Value Comments XAI in Service Name AdjustmentMaintenance This service is used to change data associated with adjustment transactions. Transaction Type Update Cancel Checked Cancel check box checked Adjustment ID Example: 078644601179 The key value of the adjustment for which you wish to test the cancel service. Cancel Reason Example: APVC AP Void Check cancel reason. This must be configured cancel reason. Click the submit button and review the results.